Deployment Workflow Log
By default, whenever you deploy a Cloudhouse Alchemy Compatibility Package using Cloudhouse.Container.Deployment.exe, the Deployment Log Cloudhouse.Deployment.log is created in the same folder that the Compatibility Package is being deployed from. The log is also output to the console at the same time.
Note: The Deployment Log leverages log4net. Please see their website for further information.
The configuration of the Deployment log file and its behaviour is controlled via the Cloudhouse.container.deployment.exe.config configuration file, found in the source Compatibility Package.
Note: The configuration file contains the recommended settings for a Compatibility Package, but you can modify this file to control the behavior of logging, as detailed in Configuring Logging
Log Format
The entries in the Cloudhouse.Deployment.log are formatted as follows:
%Date% %LogLevel% %Component% - %Message%"
Where:
|
Category |
Description |
|---|---|
|
|
Date and time the log file entry was written. |
|
|
Defines the type of log entry:
|
|
|
The area the log line relates to. For example, |
|
|
The message associated with the log line. |
For example:
2023-01-10 17:16:48,592 INFO ServicesComponent - Starting service installation.
Where:
-
2023-01-10 17:16:48,592– is theDate and Timethe message was written. -
INFO– is thelog level. -
ServicesComponent– is the relevantComponent. -
Starting service installation– is themessage.
Note: By default, INFO logs are created during deployment. Setting the log level to DEBUG increases the verbosity of the logs and should only be used during troubleshooting.
See the Configuring DEBUG Logging section of Configuring Logging for more information.